fix(seo): classify non-production homepages - #10

Summary

• Classify QuantAlchemy/solbeauty as a client production site with https://www.solbeauty.studio as its supported homepage.
• Classify QuantAlchemy/trading-journal as retired and require an empty GitHub homepage because Quant Companion now owns /journal.
• Extend the fleet audit, JSON receipt, Markdown receipt, and owner-action helper to enforce classified non-production homepage policies.
• Reject duplicate repository policies case-insensitively before any audit or update.
• Require an explicit string expected_homepage so missing or null values can never authorize a destructive clear.
• Document the classification contract so Morning Edge does not treat every GitHub homepage as a QuantAlchemy production surface.

Evidence

• https://www.solbeauty.studio/ returns direct HTTP 200 and declares its matching canonical URL.
• https://ben-hairstyle.vercel.app/ returns HTTP 404.
• https://trading-journal-rho-sand.vercel.app/ returns HTTP 200 but has no canonical, while /robots.txt and /sitemap.xml return HTTP 404.
• Quant Companion documents Trading Journal at https://www.quant-companion.quantalchemy.io/journal as the successor to the standalone app.

Verification

• PYTHONDONTWRITEBYTECODE=1 python3 -m unittest tests/test_seo_fleet_audit.py tests/test_update_repo_homepages.py -v -> 52 passed.
• git diff --check -> passed.
• Live fleet audit -> 8 production sites healthy, 235 fetched URLs, 205 sitemap URLs, and exactly 2 intended pre-cutover homepage findings.
• Owner-action dry run -> exactly 2 changes:
  • QuantAlchemy/solbeauty: dead Vercel URL to https://www.solbeauty.studio
  • QuantAlchemy/trading-journal: stale Vercel URL to empty homepage

Owner action required

The QuantAlchemy Ares GitHub App can read both repositories but cannot edit repository settings. The verified apply command returned HTTP 403 Resource not accessible by integration. After merge, a repository owner can run:

python3 tools/update_repo_homepages.py --apply

The helper verifies GitHub's persisted value after every write.

Risk

Low. The config change is additive. Existing production-site crawl behavior is unchanged. Until an owner applies the two GitHub settings, the live audit intentionally remains at defect status 1 with exact receipts.